Administrator Guide 2017
Update order history

Update order history means that magic5 can maintain an order history for each location on the system.  This contains one set of order details (Date and Reference) and multiple order lines, each consisting of an item (equating to a list entry), a quantity and, optionally, a price.  The order history can be made available on the device (Item Type - Extension history) so that a user can see what a customer has ordered in the past.  This template action triggers the data collected on a device to be assimilated into the order history for the location selected for the form.

Main

 Main screen for this action

*Description

A descriptive text to identify this action
*Unique name of source table

Enter the unique name of the table from which the data is to be taken.  This will be used to update the stock level.
*Order number/reference

Enter the unique name of the item type (if there is one) that contains an order reference that has been collected and sent back by the device.  For example, if the unique name is OrderRef then enter "%@OrderRef".

Conditions

This action will only be triggered if the conditions below are met. Leave blank if it is always to be executed.

Condition (1)-(4) If you wish to only run an action in a particular situation then you can use these conditions to specify them. The action will only occur if both conditions are satisfied. Typical uses are to only run an action or display an item if a particular answer has been given to one of the answers on the template.
For more help on using Display Conditions view the how-to guide.
Disable action

Tick this box to unconditionally disable this action.  This is the same as inserting a display condition that will never be fulfilled (eg. resultValue;xxx;equals;999 where there is no unique name of xxx).
Custom condition using 'and/or'

The text box under “Conditions (advanced)” allows custom conditions. These are tested in addition to any simpler conditions above.

If simple and complex conditions are both added then it will “AND” them together but each can be used on their own.

 

  • Each individual condition is the same as before (see above and how-to guide), but must be enclosed in square brackets.
    [condition type;unique name;test type;value to test] for example [resultValue;Priority;equals;High]
  • or and and test two or more conditions. NB. These are case-sensitive, OR and AND will not work
    • parentheses (curved brackets) give precedence to conditions. For example, to make A and B or C less ambiguous, use either:
      • (A and B) or C
      • A and (B or C)
  •  nesting can be used:
    • Surround each condition with [ and ]
    • Use lower-case or and and
    • Explicitly set precedence using ( and )
    • for example
      • ([resultValue;Priority;equals;High] and [resultValue;City;equals;London]) or (([resultValue;City;equals;Manchester] or [resultValue;City;equals;Leeds]) and [resultValue;Priority;equals;Medium])

Post-action processing (advanced)

After an action has finished running a file can be executed on the server. This could be, for instance, a .exe or a .bat file. Typically this would be used to insert data into another system.

File name to run Enter the full path and filename here.  Ensure that it is correctly spelt and that the file extension (such as .exe or .bat) is also correct.
Command line to run If the file specified above requires additional information on its command line, please enter it here. Contact your magic5 expert for further help.
Folder to run from Enter the full path and folder name that the executable programme needs to be launched from.
URL Instead of running an executable file locally, an http request can be sent to the URL specified here. It can contain standard variables.
HTTP verb Choose the http verb to be sent with the request to the URL specified above.  If you do not know what this is, ask your magic5 expert.
HTTP request body This will be very different in different circumstances and probably needs to defined at the implementation stage. It can contain standard variables and may contain the data entered on the form.
See Also
Update user attribute
Update location attribute
Update stock levels
Update customer attribute

Templates

Template
Template action

Item Types Explained

Item Type - Extension history

Lists

List entries